The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		May 23, 2026 7:34pm

PR Summary

Low Risk
Small UI-state fixes: adjusts permission hook loading semantics and tightens context-menu event listener cleanup; minimal surface area but could affect gating/disable states during initial load.

Overview
Prevents permission-gated UI from briefly rendering/vanishing by treating the auth session as part of the useUserPermissions loading state (sessionLoading now contributes to isLoading and blocks permission resolution until the session email is available).

Also tightens ResourceTable context-menu cleanup by removing the keydown listener immediately when Escape is pressed before clearing the menu state.

^{Reviewed by Cursor Bugbot for commit b96b7e7. Configure here.}

Greptile Summary

This PR eliminates the permission-gated breadcrumb flash by keeping dropdown items in the DOM during the session/permission hydration window (rendered as disabled) rather than unmounting and remounting them once permissions resolve. It also fixes the root cause in useUserPermissions by including isPending from useSession in the isLoading calculation so the loading state correctly covers the window where the session hasn't surfaced an email yet.

• use-user-permissions.ts: isPending: sessionLoading is now destructured from useSession and combined into isLoading: permissionsLoading || sessionLoading; sessionLoading is added to the useMemo dependency array.
• base.tsx / files.tsx: Permission-gated breadcrumb items and the "New connector" header action are now always rendered while isLoading is true, with disabled: !canEdit preventing interaction; dependent useMemo arrays are updated accordingly.
• resource.tsx: Adds contextMenuRowId state to track which row has its context menu open, surfacing it as isContextMenuTarget for row highlight and clearing via a self-removing Escape handler or pointerdown outside.

Confidence Score: 5/5

Safe to merge — the changes are narrowly scoped to loading-state guards and disabled props that are already handled by the component layer.

The core hook change correctly composes two independent loading flags, the DropdownMenuItem implementation applies pointer-events-none when data-disabled is set so disabled items cannot fire their onClick handlers, and the dependency arrays in both useMemo callbacks are kept in sync with the new value. No new API calls, no schema changes, and no side-effect paths are touched.

No files require special attention.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant Page
    participant useUserPermissions
    participant useSession
    participant Breadcrumb

    Page->>useUserPermissions: call(workspacePermissions, permissionsLoading)
    useSession-->>useUserPermissions: "{ data: null, isPending: true }"
    useUserPermissions-->>Page: "{ isLoading: true, canEdit: false }"
    Page->>Breadcrumb: "dropdownItems with disabled=true (items visible but inert)"

    Note over useSession: Session resolves
    useSession-->>useUserPermissions: "{ data: { user: { email } }, isPending: false }"
    useUserPermissions-->>Page: "{ isLoading: false, canEdit: true/false }"

    alt "canEdit = true"
        Page->>Breadcrumb: "dropdownItems with disabled=false (items become clickable)"
    else "canEdit = false"
        Page->>Breadcrumb: "dropdownItems=[] (items removed, no prior flash)"
    end

_{Reviews (2): Last reviewed commit: "fix(resource): self-remove keydown liste..." | Re-trigger Greptile}

@greptile

@cursor review